• Read PR diff
• Read file in context
• Check Mintlify conventions
• Post review

Observations

Wording redundancy (low): After the new <Warning>, the next paragraph still says:

It's recommended to use a live connection whenever possible. Import mode is not recommended, as it removes the benefits of using a semantic layer.

Since the Warning already states live connection is the only supported mode, "whenever possible" reads oddly — the only alternative the reader sees is Import mode, which the same sentence then discourages. Consider either dropping the recommendation sentence and keeping just the Import mode caveat, e.g.:

_Import mode_ is not recommended, as it removes the benefits of using a semantic layer.

Not blocking — just a tightness pass.

Link target (nit): [link-powerbi-live] points to desktop-directquery-about#live-connections, i.e. the DirectQuery page anchored to a live-connection section. The link is valid but visually inconsistent with [link-powerbi-directquery] pointing to the same base URL. If Microsoft has a dedicated live-connection overview page, that may read cleaner — but the current anchor is fine.

Trailing newline: The file still ends without a trailing newline (pre-existing, not introduced here). Minor — most linters prefer one.

Mintlify conventions: <Warning> block formatting is correct (blank lines inside the tags), root-relative links unchanged, no nav update needed.

• Read PR diff
• Read current file state
• Compare against prior commit (559bef7)
• Check Mintlify conventions
• Post review

Observations

Change is clean. The new commit replaces the entire __It's recommended to use a _live connection_ whenever possible.__ Use _DirectQuery_... paragraph with a <Warning> callout stating that Cube only supports live connection mode and DirectQuery is unsupported. This fully addresses the wording-redundancy concern from the prior review pass — the conflicting "whenever possible" / "use DirectQuery if..." prose is gone, not layered on top.

Mintlify conventions: <Warning> block has the required blank lines inside the tags (powerbi.mdx:63-68); root-relative links unchanged; no docs.json update needed.

Link targets (powerbi.mdx:88-89): [link-powerbi-live] points to desktop-directquery-about#live-connections and [link-powerbi-directquery] to the same desktop-directquery-about page. Both resolve, but it is slightly odd that the "live connection" link goes to a page whose URL slug is directquery. Functionally fine; not blocking.

Nit — trailing newline (powerbi.mdx:90): file still ends without a trailing newline. Pre-existing from the prior commit, not introduced here.

• Read PR diff
• Verified Mintlify conventions
• Checked link targets
• Posted review

Observations

Change is clean and accurate. The <Warning> callout at powerbi.mdx:63-71 clearly states the live-connection-only constraint and adds useful context that custom DAX queries are unsupported because they require DirectQuery. Wording is direct and reader-facing.

Mintlify conventions: <Warning> has the required blank lines inside the tags; link references are root-relative where appropriate; no docs.json update needed (existing page).

Nit — link target consistency (powerbi.mdx:91-92): [link-powerbi-live] points to desktop-directquery-about#live-connections — a section anchor within the DirectQuery page. Functionally correct (Microsoft documents live connection within the DirectQuery overview), but slightly odd that the "live connection" link's URL slug is directquery. Not worth changing unless Microsoft has a dedicated live-connection page.

• Read PR diff
• Verified Mintlify conventions
• Checked link targets
• Posted review

Observations

Change is clean and accurate. The <Warning> callout at powerbi.mdx:57-63 clearly states the live-connection-only constraint, calls out that both DirectQuery and Import mode are unsupported, and explains that custom DAX queries are unsupported because they require DirectQuery. Wording is direct and consistent across both copies of the page (admin/connect-to-data/visualization-tools/powerbi.mdx and docs/integrations/power-bi/index.mdx).

Mintlify conventions: <Warning> has the required blank lines inside the tags; link references are root-relative where appropriate; no docs.json update needed (existing pages).

Link target consistency: [link-powerbi-live] points to desktop-directquery-about#live-connections and [link-powerbi-directquery] to the same desktop-directquery-about page. Both resolve correctly — Microsoft documents live connection within the DirectQuery overview, so the shared base URL is appropriate.

No further changes needed.

• Read PR diff (git diff HEAD~1 HEAD)
• Verified Mintlify conventions
• Checked link targets
• Checked cross-file consistency

Observations

Consistency sweep is correct. The latest commit extends the live-connection-only message into the two DAX reference pages:

• reference/core-data-apis/dax-api/cross-view-filter.mdx — drops the ## DirectQuery mode section and the intro line claiming support in both modes, renames ## Live connection mode to ## How it works. Consistent with the PowerBI pages now stating DirectQuery is unsupported.
• reference/core-data-apis/dax-api/index.mdx — removes "in both Live connection and DirectQuery modes" from the cross-view-filter blurb.
• admin/connect-to-data/visualization-tools/powerbi.mdx and docs/integrations/power-bi/index.mdx — identical <Warning> callout in both copies; tables removed; new [link-powerbi-live] and [link-powerbi-directquery] references added.

Mintlify conventions: <Warning> blocks have the required blank lines inside the tags in both copies. Reference-style link definitions are kept tidy.

Cross-file parity: The two Power BI pages remain identical, which is the existing convention for this duplicated content.

Nit — trailing newline (both Power BI files end without \n): pre-existing, not introduced here. Not worth a separate fix.

No further changes needed.